Added DPI awareness support to VS2010+ projects #949
Conversation
|
@tvandijck Not overly sure to be honest, it was a feature request. However, it looks like it enables various functions to respond differently based on the setting. (I skimmed this page, so I could be incredibly wrong) |
|
Added documentation, is the availability right? Are we drilling down into the alpha releases? I feel like I saw that the other day, but I'm not sure what it was on. |
|
Availability should be alright... All the ideas @starkos has for the query system seem a rather large refactor and deviation from what we have currently that I'd almost argue that that is a 5.5 or even a 6.0. We are internally experimenting with that too btw, based on his ideas and test branches. The other thing I really think we should be doing is automate the release number. which basically just takes the tag number from git, and embeds that into the source code. I proposed it once as a PR, but I think at the time there was some argument about the dependency on git, which I feel is somewhat moot since we're on github, and it's just the embed script for automation, we can easily extent it to support other source control systems, or use a command line argument to use the git system, and default to the current behavior.. We could start at 5.0.0, although it'll screw us up a little bit, as we by now are at 5.0.41, but we'll figure that part out here then. We could also just start at 5.1.0, which would help us out. |
|
The Windows 10 Creators Update made additional changes to DPI awareness. There are now 4 values that are interesting:
For PerMonitorV2, the manifest should generate: I don't think PerMonitorV2 has been reflected into .vcxproj yet. It might be a good idea to change the enumeration names as "High" isn't really clear as to whether it should map to V1 or V2 rules. More details here: https://blogs.windows.com/buildingapps/2017/04/04/high-dpi-scaling-improvements-desktop-applications-windows-10-creators-update/ |
Resolves #783